-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve markup for contributors #194
Conversation
Pull Request Test Coverage Report for Build 9291478300Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you look into whether the map
I noted is doing anything meaningful? I ran through a few searches with it as-is and with it removed and don't see any difference but I'm also pretty early into my coffee...
@@ -0,0 +1,5 @@ | |||
<%= return if contributors.blank? %> | |||
|
|||
<% contributors.uniq.map do |contributor| %> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is .map
doing something here I'm not understanding?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, good call. It's probably a remnant of a previous iteration.
<p class="authors truncate-list"> | ||
<%= render partial: 'shared/authors', locals: { contributors: result_geo['contributors'] } %> | ||
</p> | ||
<span class="sr">Contributors: </span> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be a bit of a refactor to do this, so I don't think we should in this change... but if we changed result_geo
to just be result
wherever it came from we'd be able to remove some duplication and move the entire contributors logic into the shared partial instead of having geo/normal variants that are identical.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed on both counts.
Why these changes are being introduced: Authors are currently rendered within a `p` tag. This is not very semantically meaningful. Relevant ticket(s): * [GDT-284](https://mitlibraries.atlassian.net/browse/GDT-284) How this addresses that need: This refactors the contributors section to a partial and renders contributors as an unordered list. It is the same changeset that was introduced in #191, but without displaying the contributor type, which UXWS has deemed unnecessary at this time. Side effects of this change: None.
Why these changes are being introduced:
Authors are currently rendered within a
p
tag. This is not very semantically meaningful.Relevant ticket(s):
How this addresses that need:
This refactors the contributors section to a partial and renders contributors as an unordered list. It is the same changeset that was introduced in #191, but without displaying the contributor type, which UXWS has deemed unnecessary at this time.
Side effects of this change:
None.
Developer
Accessibility
New ENV
Approval beyond code review
Additional context needed to review
N/A
Code Reviewer
Code
added technical debt.
Documentation
(not just this pull request message).
Testing